Release 10.1A: OpenEdge Getting Started:
Core Business Services

OpenEdge levels of data security

The supported levels of data security include:

Database connection authorization (see the "Database security" section).
Schema authorization (see the "Database security" section).
Compile-time authorization, which requires Progress 4GL procedures to have authorization to compile with a particular database configured using a DBAUTHKEY configuration option. For information on compile-time authorization, see OpenEdge Deployment: Managing 4GL Applications and on DBAUTHKEY, see OpenEdge Data Management: Database Administration .
Run-time authorization, which includes the option to restrict the type of server (SQL or 4GL) that accesses the OpenEdge RDBMS. For information on run-time authorization, see OpenEdge Deployment: Managing 4GL Applications and on the Type of Server to Start (-ServerType) startup parameter, see OpenEdge Deployment: Startup Command and Parameter Reference .
Cryptography, which ensures that unauthorized users cannot read or change data. For more information on cryptography and the cryptographic features of the 4GL, see Chapter 3, " Cryptography."
Caution: Progress Software Corporation recommends that you use the cryptographic features of the 4GL only if you have a well-grounded understanding of cryptography and its usage. Use of cryptography without the necessary preparation can result in permanent data loss. In general, cryptography can have significant negative impact on application performance and decrease effective data compression for data stored in a database. For more information on managing data encryption and decryption, see the “Security” white paper prepared by the Progress Software Corporation Marketing Department, which can be found on the PSDN Web site.

For more information on authorization in OpenEdge, see the "Core user authentication and authorization" section.